Unfortunately, I am unable to go to this person's desk to see their setup.
From user:
I was able to export Word documents into DOORS until I recently got a PC upgrade. After a series of false starts I got the DOORS.dot file into the Word/Startup folder. After opening DOORS and the Word file I clicked on the DOORS icon and got the Microsoft Visual Basic error:
Compile error in hidden module: ExportButtonCallback
The help for this error said:
A protected module can't be displayed. This error has the following cause and solution: There is a compilation error in the code of the specified module, but it can't be displayed because the project is protected.
I went into the Word macro GUI and clicked on the Visual Basic editor. DOORSExporter (DOORS) shows up in the list but when I try to see it I get the message:
Project is unviewable.
lnorton - Wed May 06 14:53:48 EDT 2009 |
|
Re: Problem with DOORS macro for importing Word into DOORS
Ron_Lewis - Wed May 06 16:00:04 EDT 2009
Probably would help if you include info on old operating system, old office version
and new operating system and new office version.
The visual basic that Telelogic provides is password protected so you can't view the code.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
lnorton - Wed May 06 16:08:53 EDT 2009 Ron_Lewis - Wed May 06 16:00:04 EDT 2009
Probably would help if you include info on old operating system, old office version
and new operating system and new office version.
The visual basic that Telelogic provides is password protected so you can't view the code.
I've handed it to IT and told them contact IBM.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
Tony_Goodman - Thu May 07 03:06:46 EDT 2009 lnorton - Wed May 06 16:08:53 EDT 2009
Yeah, thanks. This is a classified lab and I don't work on the same plant site...I was hoping someone may have something similar that was a quick "Set Security to Low" type of thing.
I've handed it to IT and told them contact IBM.
Contact IT again and verify that they installed DOORS after MS Office.
This should have put the doors.dot into the startup folder automatically.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
lnorton - Thu May 07 10:50:09 EDT 2009 Tony_Goodman - Thu May 07 03:06:46 EDT 2009
I suspect that DOORS was installed before MS Office.
Contact IT again and verify that they installed DOORS after MS Office.
This should have put the doors.dot into the startup folder automatically.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
llandale - Thu May 07 10:53:41 EDT 2009
I have a nagging memory of this being a DOORS.dot version mis-match problem. Perhaps you have the v7.1 doors.dot in your startup folder, but are using v8.3.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
lnorton - Thu May 07 10:58:43 EDT 2009 llandale - Thu May 07 10:53:41 EDT 2009
I have a nagging memory of this being a DOORS.dot version mis-match problem. Perhaps you have the v7.1 doors.dot in your startup folder, but are using v8.3.
However, I am starting to think it is an issue with DOORS 7.1 and possibly a newer version of Word. I'm looking into that now.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
Peter_Albert - Fri May 08 06:10:37 EDT 2009 lnorton - Thu May 07 10:58:43 EDT 2009
I don't think so, because they are a classified lab and can only install previously installed "third-party" (meaning not MS stuff, I guess) software.
However, I am starting to think it is an issue with DOORS 7.1 and possibly a newer version of Word. I'm looking into that now.
For the moment, I would recommend to try to start DOORS and the Windows exporter from a user with local admin rights once, and see whether that fixes it for all users.
Regards,
Peter
|
|
Re: Problem with DOORS macro for importing Word into DOORS
llandale - Fri May 08 09:24:49 EDT 2009
I knew this sounded familiar. Looked through my old emails:
"To solve an Word-Export-To-DOORS problem "Compile error in hidden module: ExportButtonCallback", according to Telelogic Support and Louie Landale, please have someone with Admin rights log into my laptop and attempt to export an MS-Word file to DOORS. To do that, I'll need to log into DOORS after you log into the computer, and I'll have to find a suitable MS-Word file for Export. It is expected that this one-time export will set Registry entries that will remain available to other users exporting in the future."
>Louie
|
|
Re: Problem with DOORS macro for importing Word into DOORS
InProcess - Tue Sep 29 12:24:15 EDT 2009 llandale - Fri May 08 09:24:49 EDT 2009
I knew this sounded familiar. Looked through my old emails:
"To solve an Word-Export-To-DOORS problem "Compile error in hidden module: ExportButtonCallback", according to Telelogic Support and Louie Landale, please have someone with Admin rights log into my laptop and attempt to export an MS-Word file to DOORS. To do that, I'll need to log into DOORS after you log into the computer, and I'll have to find a suitable MS-Word file for Export. It is expected that this one-time export will set Registry entries that will remain available to other users exporting in the future."
>Louie
Louie pointed me in the right direction with his comment. There are registry entries which need to be added for the export to work. However, the registry entries aren't added during the export. They are actually added the first time the DOORS client is loaded. It is not necessary to login to the DOORS database though.
The problem under Windows Vista is that the DOORS client has to be run with administrator privileges in order to update the registry. Once the registry entries are added to export will work without running the DOORS client with administrator privileges. By taking snapshots of the registry, I was able to determine the specific registry entries which need to be added for the export to work using the DOORS 8.3 client.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
kbmurphy - Tue Sep 29 13:38:26 EDT 2009 InProcess - Tue Sep 29 12:24:15 EDT 2009
I encountered this error when attempting to export data from Microsoft Word 2007 using the DOORS 8.3 client under Windows Vista with User Access Control (UAC) enabled. However, I suspect that this problem isn't specific to these product versions.
Louie pointed me in the right direction with his comment. There are registry entries which need to be added for the export to work. However, the registry entries aren't added during the export. They are actually added the first time the DOORS client is loaded. It is not necessary to login to the DOORS database though.
The problem under Windows Vista is that the DOORS client has to be run with administrator privileges in order to update the registry. Once the registry entries are added to export will work without running the DOORS client with administrator privileges. By taking snapshots of the registry, I was able to determine the specific registry entries which need to be added for the export to work using the DOORS 8.3 client.
|
|
Re: Problem with DOORS macro for importing Word into DOORS
InProcess - Tue Sep 29 17:57:30 EDT 2009 kbmurphy - Tue Sep 29 13:38:26 EDT 2009
Mind posting those registry settings?
Attachments
attachment_14300225_Doors83Word2007VistaExportFix_reg.txt
|
|